⚠️ Unpublished: This item is from a solution that is not yet published on Azure Marketplace or not installed in Content Hub.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | NonameSecurityMicrosoftSentinel |
| Publisher | Noname Security |
| Used in Solutions | Noname API Security Solution for Microsoft Sentinel |
| Collection Method | REST Pull API |
| Connector Definition Files | Connector_RESTAPI_NonameSecurity.json |
| Ingestion API | HTTP Data Collector API — Connector definition requires workspace key (SharedKey pattern) |
| Custom Log V1 Tables | Yes 🔶 — ingests into tables with type-suffixed columns |
Noname Security solution to POST data into a Microsoft Sentinel SIEM workspace via the Azure Monitor REST API
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
NonameAPISecurityAlert_CL 🔶 |
? | ✓ | ? |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Resource Provider Permissions:
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
1. Configure the Noname Sentinel integration.
Configure the Sentinel workflow in the Noname integrations settings. Find documentation at https://docs.nonamesecurity.com
WorkspaceIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
PrimaryKeyNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊